Beat you to it 😉 #1378

Weird (unrelated) kem failure there: https://github.com/RustCrypto/traits/actions/runs/6836704964/job/18591915685?pr=1379

Of course it breaks right after I approve!

Ugh, yeah workspaces with mixed pre-and-post 1.60 crates aren't fun. FWIW I've put the other crates which use weak feature activation and/or namespacing in an exclude: https://github.com/RustCrypto/traits/blob/master/Cargo.toml#L15

I guess at some point we might consider bumping all of the crates in the workspace to at least 1.60 because otherwise it's an enormous pain.

@newpavlov if you remove my suggested getrandom line, I'd be happy to take care of adding it back, which would also simplify this PR

@tarcieri
It's probably better to simply update aead to use crypto-common v0.2.0-pre.

@newpavlov you'll also have to update universal-hash which has the same problem.

I opened #1380 to swap how members and exclude are currently being used.

@tarcieri
I am not sure why, but universal-hashes CI passes without issues.

Duh... Updating aead to crypto-common v0.2 will be slightly more involved than I thought, so I will follow your recomendation and will remove the use of namespaced features.

Aah, universal-hash is already using the rm ../Cargo.toml trick